Use this option to enable enterprise specific traps in a specified community. Enterprise specific traps indicate that some enterprise specific event has occurred. The specific-trap field identifies the particular trap that occurred. For example, when configured to do so, ELS event messages are sent in enterprise-specific traps.
Enter the community name.
Valid Values: a string of 1 to 31 alphanumeric characters.
Characters such as
spaces, tabs, or Default Value: public
Select the Submit button.
Use this option to disable specified traps or all traps.
Enter the community name.
Valid Values: a string of 1 to 31 alphanumeric characters. Characters such as
spaces, tabs, or Default Value: public
Select the Submit button.
Use this option to
disable cold start traps in a specified community. A cold start
trap means that the transmitting router is reinitializing and that
the agent's configuration or the protocol entity implementation may be
altered.
Enter the community name.
Valid Values: a string of 1 to 31 alphanumeric characters. Characters such as
spaces, tabs, or Default Value: public
Select the Submit button.
Use this option to
disable warm start traps in a specified community. A warm start
trap means that the transmitting router is reinitializing, but the
configuration or protocol implementation will remain the same.
Enter the community name.
Valid Values: a string of 1 to 31 alphanumeric characters.
Characters such as
spaces, tabs, or Default Value: public
Select the Submit button.
Use this option to
disable link_down traps in a specified community. A link_down trap
(2) recognizes a failure in one of the communication links represented
in the agent's configuration. The link_down trap-PDU
contains the name and value of the ifIndex instance for the affected
link as the first element of its variable-bindings.
Enter the community name.
Valid Values: a string of 1 to 31 alphanumeric characters.
Characters such as
spaces, tabs, or Default Value: public
Select the Submit button.
Use this option to
disable link_up traps in a specified community. A link_up trap
recognizes that a previously inactive link in the network has come up.
The link_up trap-PDU contains the name and value of the ifIndex
instance for the affected link as the first element of its
variable-bindings.
Enter the community name.
Valid Values: a string of 1 to 31 alphanumeric characters.
Characters such as
spaces, tabs, or Default Value: public
Select the Submit button.
Use this option to
disable authentication failure traps for a specified community.
Authentication failure traps indicate that the sender of the SNMP
request does not have the proper permission to talk to this box's
SNMP agent.
Enter the community name.
Valid Values: a string of 1 to 31 alphanumeric characters.
Characters such as
spaces, tabs, or Default Value: public
Select the Submit button.
Use this option to
disable egp neighbor loss traps in a specified community. EGP
Neighbor Loss traps recognize that an EGP neighbor and peer has been
marked down and is no longer a peer. The egpNeighborLoss trap-PDU
contains the name and value of the egpNeighAddr instance for the
affected neighbor as the first element of its variable-bindings.
Enter the community name.
Valid Values: a string of 1 to 31 alphanumeric characters.
Characters such as
spaces, tabs, or Default Value: public
Select the Submit button.
Use this option to
disable enterprise specific traps in a specified community.
Enterprise specific traps indicate that some enterprise specific event
has occurred. The specific-trap field identifies the particular
trap that occurred. For example, when configured to do so, ELS event
messages are sent in enterprise-specific traps.
Enter the community name. Valid Values: a string of 1 to 31 alphanumeric characters.
Characters such as
spaces, tabs, or Default Value: public
Select the Submit button.
Use this option to cause the BGP speaker to aggregate a block of
addresses and advertise a single route to its BGP neighbors. You must
specify the network prefix common to all the
routes being aggregated and the network mask
for the routes.
Valid Values: any valid IP address
Default Value: none
Valid Values: any valid IP address
Default Value: none
Select the Submit button.
Use this option to define a list of BGP4 neighbors to this BGP4
autonomous system (AS).
Neighbors are routers with which a speaker establishes
a connection.
Once neighbors are defined, connections to them are established by
default.
You define the neighbor's address, AS number, and
other parameters that define the neighbor to this BGP speaker.
Valid Values: any valid IP address
Default Value: none
Valid Values: an integer in the range of [0 - 65535]
Default Value: 0
Valid Values: 0 to 65535 seconds
Default Value: 12 seconds
Valid Values: 0 to 65535 seconds
Default Value: 120 seconds
Once neighbors have established BGP connection, they exchange
Keep-alive messages at frequent intervals to ensure that the connection
is
still alive and the neighbors are reachable.
The Keep-Alive timer interval is calculated
to be one-third of the negotiated hold timer value.
Hence the hold timer value must be either zero or at least three
seconds.
Note that on switched lines, you may wish to have the
Hold Timer value of zero to save bandwidth by not
sending Keep-Alives at frequent intervals.
Valid Values: 0 to 65535 seconds
Default Value: 90 seconds
Valid Values: 0 to 65535
Default Value: 1024
Select the Submit button.
Enter the AS number.
Valid Values: 0 to 65535
Default Value: 0
Select the Submit button.
Use this option to create
a policy that determines whether a specific address, or range
of addresses, can be imported to the BGP speaker's routing table
from the IGP routing table.
Exclusive policies prevent route information from being
included in the BGP speaker's routing table.
Valid Values: any valid IP address
Default Value: none
Valid Values: any valid IP address
Default Value: none
This is the value that has been set for a particular AS. Tag values
match that of the AS from which they were learned.
Valid Values: 0 to 65535
Default Value: 0
Select the Submit button.
Use this option to create
a policy that determines whether a specific address, or range
of addresses, can be imported to the BGP speaker's routing table
from the IGP routing table.
Inclusive policies ensure that specific routes will be
included in the BGP speaker's routing table.
Valid Values: any valid IP address
Default Value: none
Valid Values: any valid IP address
Default Value: none
This is the value that has been set for a particular AS. Tag values
match that of the AS from which they were learned.
Valid Values: 0 to 65535
Default Value: 0
Select the Submit button.
Exclusive policies prevent route information from being
included in the BGP speaker's routing table.
Valid Values: any valid IP address
Default Value: none
Valid Values: any valid IP mask
Default Value: none
Valid Values: 0 to 65535
Default Value: 0
Valid Values: 0 to 65535
Default Value: 0
Select the Submit button.
Inclusive policies ensure that specific routes will be
included in the BGP speaker's routing table.
Valid Values: any valid IP address
Default Value: none
Valid Values: any valid IP mask
Default Value: none
Valid Values: 0 to 65535
Default Value: 0
Valid Values: 0 to 65535
Default Value: 0
Valid Values: 0 to 65535
Default Value: 0
Select the Submit button.
Decisions on which route information to export are made on explicitly
defined policy statements.
Send policies enable you to select the route information to
export to peers. Exportable information can include information
collected from neighboring autonomous systems.
Use this option to create policies that
determine which of the BGP speaker's learned routes will be
readvertised.
These routes could be internal or external to the BGP speaker's AS.
Exclusive policies prevent route information from being
included in the BGP speaker's routing table.
Valid Values: any valid IP address
Default Value: none
Valid Values: any valid IP address
Default Value: none
This is the value that has been set for a particular AS. Tag values
match that of the AS from which they were learned.
Valid Values: 0 to 65535
Default Value: 0
Valid Values: 0 to 65535
Default Value: 0
Select the Submit button.
Use this option to create policies that
determine which of the BGP speaker's learned routes will be
readvertised.
These routes could be internal or external to the BGP speaker's AS.
Inclusive policies ensure that specific routes will be
included in the BGP speaker's routing table.
Valid Values: any valid IP address
Default Value: none
Valid Values: any valid IP address
Default Value: none
This is the value that has been set for a particular AS. Tag values
match that of the AS from which they were learned.
Valid Values: 0 to 65535
Default Value: 0
Valid Values: 0 to 65535
Default Value: 0
Select the Submit button.
Use this option to change a BGP configuration
item previously installed by the add command.
The change causes the current aggregate to use a different network
prefix and mask to aggregate specific routes or all routes in an
address range.
Enter the index of the aggregate to be modified.
Select the Submit button.
Use this option to change a BGP configuration
item previously installed by the add command.
The change causes the current neighbor address to be changed to the
one specified.
Enter the neighbor address to be modified.
Valid Values: any valid IP address
Default Value: none
Select the Submit button.
Use this option to alter an existing originate
policy definition.
Enter the index of the originate-policy to be modified.
Select the Submit button.
Use this option to alter an existing originate
policy definition.
Enter the index of the receive-policy to be modified.
Select the Submit button.
Use this option to alter an existing send policy
to one that is more inclusive, or more exclusive.
You must enter the index of send-policy to be modified, and provide
the policy type (Exclusive or Inclusive).
Enter the index of the send-policy to be modified.
Select the Submit button.
Use this option to delete an existing aggregate
definition.
Enter the index number of the aggregate you want to delete.
The index number is equivalent to the AS number.
Select the Submit button.
Use this option to delete a BGP neighbor.
Enter the neighbor's network address to be deleted.
Valid Values: any valid IP address
Default Value: none
Select the Submit button.
Use this option to delete the no-receive policy set
up for a particular AS.
Enter the AS number.
Valid Values: 0 to 65535
Default Value: 0
Select the Submit button.
Use this option to delete a specific originate
policy.
Enter the index number of the originate policy.
Select the Submit button.
Use this option to delete a specific receive
policy.
Enter the index number of the receive policy.
Select the Submit button.
Use this option to delete a specific send
policy.
Enter the index number of the send policy.
Select the Submit button.
Use this option to disable a previously enabled BGP
neighbor.
Enter the neighbor address.
Valid Values: any valid IP address
Default Value: none
Select the Submit button.
BGP is an exterior gateway routing protocol used to
exchange
network reachability information among autonomous systems (AS).
An AS is essentially a collection of routers and endnodes
that operate under a single administrative organization.
Within each AS, routers and endnodes share routing information using an
interior gateway protocol.
The interior gateway protocol may be either RIP or OSPF.
BGP was introduced in the Internet in the loop-free exchange of
routing information between autonomous systems.
Based on Classless Inter-Domain Routing (CIDR),
BGP has since evolved to support the aggregation and
reduction of routing information.
CIDR is a strategy designed to address the following
problems:
CIDR eliminates the concept of address classes, and provides a
method for summarizing n different routes into single routes.
This significantly reduces the amount of routing information that BGP
routers must store and exchange.
Note: IBM only supports the latest version of BGP -
BGP4, which is defined in RFC 1654.
Use this option to enable the BGP protocol.
Valid Values: 0 to 65535
Default Value: 0
Valid Values: 0 to 65535
Default Value: 1024
Select the Submit button.
Neighbors are routers with which a speaker establishes
a connection.
Once neighbors are defined, connections to them are established by
default.
Use Enable Neighbor to enable a BGP neighbor.
Enter the neighbor address.
Valid Values: any valid IP address
Default Value: none
Select the Submit button.
Use this option to change the order in which
aggregates have been defined. This changes the order in which the
router applies existing policies to route information. Before selecting
Move Aggregate, select List
to see what policies have been defined.
Enter the index of the aggregate to move
and the record
number to move AFTER number.
Select the Submit button.
Enter the index of the originate-policy to move
and the record
number to move AFTER.
Select the Submit button.
Use this option to change the order in which
policies have been defined. This changes the order in which the
router applies existing policies to route information. Before selecting
Move Receive-Policy, it is advisable to select
List to see what policies have been defined.
Enter the index of the originate-policy to move
and the record
number to move AFTER.
Select the Submit button.
Use this option to change the order in which
policies have been defined. This changes the order in which the
router applies existing policies to route information. Before selecting
Move Send-Policy, it is advisable to select
List to see what policies have been defined.
Enter the index of the originate-policy to move
and the record
number to move AFTER.
Disable Trap All
Disable Trap Cold_Start
Disable Trap Warm_Start
Disable Trap Link_Down
Disable Trap Link_Up
Disable Trap Auth_Fail
Disable Trap EGP
Disable Trap Enterprise
Add Aggregate
Add Neighbor
Add No-Receive ASnum
Use this option to define a list of BGP4 autonomous system(AS) paths
that the device will exclude from the BGP routing tables
if the particular AS number appears anywhere inside
the AS-path list.
Add Originate-Policy (Exclusive)
Add Originate-Policy (Inclusive)
Add Receive-Policy (Exclusive)
Decisions on which reachability information to accept are made on
explicitly defined policy statements.
Use this to determine what
routes will be imported to the BGP speaker's routing table.
Add Receive-Policy (Inclusive)
Decisions on which reachability information to accept are made on
explicitly defined policy statements.
Use this option to determine what
routes will be imported to the BGP speaker's routing table.
Add Send-Policy (Exclusive)
Add Send-Policy (Inclusive)
Change Aggregate
Change Neighbor
Change Originate-Policy
Change Receive-Policy
Change Send-Policy
Delete Aggregate
Delete Neighbor
Delete No-Receive
Delete Originate-Policy
Delete Receive-Policy
Delete Send-Policy
Disable Neighbor
Enable BGP
Enable Neighbor
Move Aggregate
Move Originate-Policy
Use this option to change the order in which
policies have been defined. This changes the order in which the
router applies existing policies to route information. Before selecting
Move Originate-Policy, it is advisable to select
List to see what policies have been defined.
Move Receive-Policy
Move Send-Policy